-
Notifications
You must be signed in to change notification settings - Fork 3
feat(sdk): initial obligations support in rewrap flow #748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: jakedoublev <[email protected]>
Signed-off-by: jakedoublev <[email protected]>
2173ca8
to
2fe0892
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: jakedoublev <[email protected]>
20c4c05
to
45c7127
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: jakedoublev <[email protected]>
Signed-off-by: jakedoublev <[email protected]>
7f6e8c0
to
d1480b9
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Signed-off-by: jakedoublev <[email protected]>
80ea30a
to
b19ec8e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
71084e3
to
8b3d2c0
Compare
This comment was marked as resolved.
This comment was marked as resolved.
1 similar comment
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: jakedoublev <[email protected]>
7b91fdd
to
ed3b4a5
Compare
3/4 of the Sonarcloud issues are existing code I only touched, and the 4th asking for DRYness within the ZTDFReader and NanoTDFReader I would rather avoid because they satisfy the same interface but may differ in implementation as Nano is aligned with other ZTDF features like splits and streaming. |
If these changes look good, signoff on them with:
If they aren't any good, please remove them with:
|
Signed-off-by: jakedoublev <[email protected]>
Signed-off-by: jakedoublev <[email protected]>
98ca20b
to
bbebc87
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to have Nick or Eugene review too, looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left small inline comments that can be addressed later on, non-blocking from merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This definitely seems fine, and like it will work. From an API standpoint, I'm not sure I'm fond of mixing setting this.requiredObligations
in with a call to decrypt
. I think it could always be cleaned up later though.
f84b41b
|
X-Rewrap-Additional-Context
to KAS.Rewrap during decrypt from client config or reader config specifiedfulfillableObligationFQNs
(with reader config obligations taking preference as most granular specificity)obligations()
method that retrieves obligations through the rewrap flow